Dear Fabien

thanks for your interest in my question.

i will try to be precise in my explanation:

pov objects are created using descriptions of their shapes, position,
rotation and scale in space, and their surface properties. these
descriptions can be parametrized (if i can use the verb) in order to
make the object generic, and relate it to others thus have knowledge in
them: 

e.g. the diameter of a greek doric column is equal to the tenth (1/10)
of its height.

thus the declaration of my column object in povray would be as follow:
#declare height=3
#declare diameter=(height)/10
#declare column=
cylinder{ <0,0,0,>, <0,height,0>, (diameter)/2}

so every time i change the height of my column, the diameter changes 
accordingly. so both variables are related to each other in a very
specific way (knowledge), which constitutes an architectural type: the
doric order. 

so every time i encounter a column that obeys to this type of relations,
i can confirm that it is a doric column. the principle can be applied to
other concepts like: symmetry, hierarchy, rhythm, study of proportions,
perception of forms, construction rules, etc... and lots of
architectural principles and concepts.

a povray file contains specifications of architectural objects, and
knowledge extraction (the approach i hope to develop) is to find a way
to extract all the knowledge (principles, concepts and rules) in this
file and synthesize it to produce clear definitions of the objects
contained within. (maybe using C or C++ algorithms, or LISP, or any
other suitable programming language)

i am not a programmer but i am working on it, that is why i need some
orientations.

feel free to reply
Hassoun

Fabien Mosen wrote:
> 
> Err...
> could you explain what "knowledge extraction" means ?
> Then, -maybe-, I could answer..
> 
> Fabien.

Post a reply to this message